I move between the library and the journeys it serves. A component is only useful if its states, content and behavior work within the product.
Audit patterns and ownership
I review screens and journeys for repeated patterns, conflicting styles and missing states. I also consider how the product is built and who will maintain the system, so shared rules fit the team’s workflow.
Define foundations and tokens
I establish typography, color roles, spacing and semantic tokens. I prioritize foundations and components that affect many parts of the experience or create repeated production work.
Build components and guidance
I define purposeful variants, interaction states and responsive behavior. In Figma, I use variables and auto layout to express these relationships. Documentation covers usage, content expectations and exceptions, with the design model aligned to implementation.
Test the system in use
I apply components to complete journeys, long labels, validation messages, empty states and narrow screens. I review the effects of shared changes and use feedback from the people working with the library to refine the rules.
The system should preserve the product’s visual identity while reducing repeated decisions. I look for fewer contradictions, clearer handoffs and components the team can maintain.
About
Me
I bring together product thinking, visual identity and interaction design, with close attention to context, clarity and the details that make an experience feel considered.
Read more